Methods and Systems for Providing User Feedback

ABSTRACT

A method displays a first story, which is a republication of a second story and an indication of a previous user interaction with the second story that resulted in creating the first story. The method displays a compressed view of a first user-feedback interface, corresponding to the first story, including affordances for providing user feedback regarding the first story, and displays a compressed view of a second user-feedback interface, corresponding to the second story, including affordances for providing user feedback regarding the second story. The method detects user selection of either the first user-feedback interface or the second user-feedback interface. In response, the method displays an expanded view of the selected user-feedback interface while displaying the compressed view of the user-feedback interface not selected. The expanded view includes the affordances corresponding to the selected user-feedback interface and replaces a portion of the story corresponding to the user-feedback interface not selected.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/728,838, filed Jun. 2, 2015, entitled “Methods and Systems forProviding User Feedback,” which is incorporated by reference herein inits entirety.

TECHNICAL FIELD

This application relates generally to providing user feedback, includingbut not limited to concurrently displaying user-feedback interfaces forproviding user feedback on electronic content.

BACKGROUND

The Internet has become an increasingly dominant platform for thepublication of electronic content, for both the media and the generalpopulation. At the same time, enabling users to interact with suchpublished electronic content has become an increasingly importantfeature for online services, such as social networks, to implement.

Given the abundance of published electronic content, users oftenstruggle to provide user feedback in an efficient manner.

SUMMARY

Accordingly, there is a need for methods, systems, and interfaces forproviding user feedback on electronic content in a simple and efficientmanner. By concurrently displaying multiple user-feedback interfacescorresponding to multiple stories, such as news articles and userrepublications of news articles, users can efficiently and easilyprovided feedback for the stories. Such methods and interfacesoptionally complement or replace conventional methods for providing userfeedback.

In accordance with some embodiments, a method is performed at a clientdevice with one or more processors and memory storing instructions forexecution by the one or more processors. The method includes displayinga first story, wherein the first story includes a second story and anindication of a previous user interaction with the second story thatresulted in creation of the first story. A first user-feedback interfacecorresponding to the first story and a second user-feedback interfacecorresponding to the second story are concurrently displayed. The firstuser-feedback interface comprises one or more first affordances forproviding user feedback regarding the first story and the seconduser-feedback interface comprises one or more second affordances forproviding user feedback regarding the second story. The method includesreceiving user feedback for the first story through the firstuser-feedback interface or for the second story through the seconduser-feedback interface. When the user feedback is received through thefirst user-feedback interface, notification is sent to a server toassociate the user feedback with the first story. When the user feedbackis received through the second user-feedback interface, notification issent to the server to associate the user feedback with the second story.

In accordance with some embodiments, a client device includes one ormore processors, memory, and one or more programs; the one or moreprograms are stored in the memory and configured to be executed by theone or more processors. The one or more programs include instructionsfor performing the operations of the method described above. Inaccordance with some embodiments, a non-transitory computer-readablestorage medium has stored therein instructions that, when executed bythe electronic device, cause the electronic device to perform theoperations of the method described above.

Thus, client devices are provided with more effective and efficientmethods for providing user feedback for stories, thereby increasing theeffectiveness and efficiency of such devices and user satisfaction withsuch devices.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings. Like reference numerals referto corresponding parts throughout the figures and description.

FIG. 1 is a block diagram illustrating an exemplary network architectureof a social network in accordance with some embodiments.

FIG. 2 is a block diagram illustrating an exemplary social-networksystem in accordance with some embodiments.

FIG. 3 is a block diagram illustrating an exemplary client device inaccordance with some embodiments.

FIGS. 4A-4H illustrate exemplary graphical user interfaces (GUIs) on aclient device for providing user feedback, in accordance with someembodiments.

FIGS. 5A-5E are flow diagrams illustrating a method of providing userfeedback in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made to embodiments, examples of which areillustrated in the accompanying drawings. In the following description,numerous specific details are set forth in order to provide anunderstanding of the various described embodiments. However, it will beapparent to one of ordinary skill in the art that the various describedembodiments may be practiced without these specific details. In otherinstances, well-known methods, procedures, components, circuits, andnetworks have not been described in detail so as not to unnecessarilyobscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are used onlyto distinguish one element from another. For example, a firstuser-feedback interface could be termed a second user-feedbackinterface, and, similarly, a second user-feedback interface could betermed a first user-feedback interface, without departing from the scopeof the various described embodiments. The first user-feedback interfaceand the second user-feedback interface are both user-feedbackinterfaces, but they are not the same user-feedback interface.

The terminology used in the description of the various embodimentsdescribed herein is for the purpose of describing particular embodimentsonly and is not intended to be limiting. As used in the description ofthe various described embodiments and the appended claims, the singularforms “a,” “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting”or “in accordance with a determination that,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event]” or “in accordance with a determination that [astated condition or event] is detected,” depending on the context.

As used herein, the term “exemplary” is used in the sense of “serving asan example, instance, or illustration” and not in the sense of“representing the best of its kind.”

FIG. 1 is a block diagram illustrating an exemplary network architecture100 of a social network in accordance with some embodiments. The networkarchitecture 100 includes a number of client devices (also called“client systems,” “client computers,” or “clients”) 104-1, 104-2, . . .104-n communicably connected to an electronic social-network system 108by one or more networks 106 (e.g., the Internet, cellular telephonenetworks, mobile data networks, other wide area networks, local areanetworks, metropolitan area networks, and so on). In some embodiments,the one or more networks 106 include a public communication network(e.g., the Internet and/or a cellular data network), a privatecommunications network (e.g., a private LAN or leased lines), or acombination of such communication networks.

In some embodiments, the client devices 104-1, 104-2, . . . 104-n arecomputing devices such as smart watches, personal digital assistants,portable media players, smart phones, tablet computers, 2D gamingdevices, 3D (e.g., virtual reality) gaming devices, laptop computers,desktop computers, televisions with one or more processors embeddedtherein or coupled thereto, in-vehicle information systems (e.g., anin-car computer system that provides navigation, entertainment, and/orother information), and/or other appropriate computing devices that canbe used to communicate with the social-network system 108. In someembodiments, the social-network system 108 is a single computing devicesuch as a computer server, while in other embodiments, thesocial-network system 108 is implemented by multiple computing devicesworking together to perform the actions of a server system (e.g., cloudcomputing).

Users 102-1, 102-2, . . . 102-n employ the client devices 104-1, 104-2,. . . 104-n to access the social-network system 108 and to participatein a corresponding social-networking service provided by thesocial-network system 108. For example, one or more of the clientdevices 104-1, 104-2, . . . 104-n execute web browser applications thatcan be used to access the social-networking service. As another example,one or more of the client devices 104-1, 104-2, . . . 104-n executesoftware applications that are specific to the social-networking service(e.g., social-networking “apps” running on smart phones or tablets, suchas a Facebook social-networking application running on an iPhone,Android, or Windows smart phone or tablet).

Users interacting with the client devices 104-1, 104-2, . . . 104-n canparticipate in the social-networking service provided by thesocial-network system 108 by providing and/or consuming (e.g., posting,writing, viewing, publishing, broadcasting, promoting, recommending,sharing, commenting on, liking) digital content, such as text comments(e.g., statuses, updates, announcements, replies, location “check-ins,”private/group messages), photos, videos, audio files, links (e.g., toweb pages, articles, etc.), documents, and/or other electronic content.Users of the social-networking service can also annotate informationposted by other users of the social-networking service (e.g., endorsingor “liking” a posting of another user, or commenting on a post byanother user or publishing source). In some embodiments, information canbe posted on a user's behalf by systems and/or services external to thesocial-network system 108. For example, the user may post a review of amovie to a movie-review website, and with proper permissions thatwebsite may cross-post the review to the social network system 108 onthe user's behalf. In another example, a software application executingon a mobile client device, with proper permissions, may use globalpositioning system (GPS) or other geo-location capabilities (e.g., Wi-Fior hybrid positioning systems) to determine the user's location andupdate the social network system 108 with the user's location (e.g., “AtHome”, “At Work”, or “In San Francisco, Calif.”), and/or update thesocial network system 108 with information derived from and/or based onthe user's location. Users interacting with the client devices 104-1,104-2, . . . 104-n can also use the social-networking service providedby the social-network system 108 to define groups of users. Usersinteracting with the client devices 104-1, 104-2, . . . 104-n can alsouse the social-networking service provided by the social-network system108 to communicate and collaborate with each other.

In some embodiments, the network architecture 100 also includesthird-party servers 110-1, 110-2, . . . 110-m. In some embodiments, agiven third-party server 110 is used to host third-party websites thatprovide web pages to client devices 104, either directly or inconjunction with the social-network system 108. In some embodiments, thesocial-network system 108 uses inline frames (“iframes”) to nestindependent websites within a user's social network session. In someembodiments, a given third-party server is used to host third-partyapplications that are used by client devices 104, either directly or inconjunction with the social-network system 108. In some embodiments, thesocial-network system 108 uses iframes to enable third-party developersto create applications that are hosted separately by a third-partyserver 110, but operate within a social-networking session of a user 102and are accessed through the user's profile in the social-network system108. Exemplary third-party applications include applications for books,business, communication, contests, education, entertainment, fashion,finance, food and drink, games, health and fitness, lifestyle, localinformation, movies, television, music and audio, news, photos, video,productivity, reference material, security, shopping, sports, travel,utilities, and the like. In some embodiments, a given third-party server110 is used to host enterprise systems, which are used by client devices104, either directly or in conjunction with the social-network system108. In some embodiments, a given third-party server 110 is used toprovide third-party content (e.g., news articles, reviews, messagefeeds, etc.).

In some embodiments, a given third-party server 110 is a singlecomputing device, while in other embodiments, a given third-party server110 is implemented by multiple computing devices working together toperform the actions of a server system (e.g., cloud computing).

FIG. 2 is a block diagram illustrating an exemplary social-networksystem 108 in accordance with some embodiments. The social-networksystem 108 typically includes one or more processing units (processorsor cores) 202, one or more network or other communications interfaces204, memory 206, and one or more communication buses 208 forinterconnecting these components. The communication buses 208 optionallyinclude circuitry (sometimes called a chipset) that interconnects andcontrols communications between system components. The social-networksystem 108 optionally includes a user interface (not shown). The userinterface, if provided, may include a display device and optionallyincludes inputs such as a keyboard, mouse, trackpad, and/or inputbuttons. Alternatively or in addition, the display device includes atouch-sensitive surface, in which case the display is a touch-sensitivedisplay.

Memory 206 includes high-speed random-access memory, such as DRAM, SRAM,DDR RAM, or other random-access solid-state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, and/orother non-volatile solid-state storage devices. Memory 206 mayoptionally include one or more storage devices remotely located from theprocessor(s) 202. Memory 206, or alternately the non-volatile memorydevice(s) within memory 206, includes a non-transitory computer-readablestorage medium. In some embodiments, memory 206 or the computer-readablestorage medium of memory 206 stores the following programs, modules anddata structures, or a subset or superset thereof:

-   -   an operating system 210 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a network communication module 212 that is used for connecting        the social-network system 108 to other computers via the one or        more communication network interfaces 204 (wired or wireless)        and one or more communication networks (e.g., the one or more        networks 106);    -   a social network database 214 for storing data associated with        the social network, such as:        -   entity information 216, such as user information 218;        -   connection information 220; and        -   content 222, such as:    -   user content 224, which includes user feedback 224-1; and/or    -   news articles 226, which includes user feedback;    -   a social network server module 228 for providing        social-networking services and related features (e.g., in        conjunction with browser module 338 or social network client        module 340 on the client device 104, FIG. 3), which includes:        -   a login module 230 for logging a user 102 at a client 104            into the social-network system 108; and        -   a content feed manager 232 for providing content to be sent            to clients 104 for display, which includes:            -   a content generator module 234 for adding objects to the                social network database 214, such as images, videos,                audio files, comments, status messages, links,                applications, and/or other entity information 216,                connection information 220, or content 222; and            -   a content selector module 236 for choosing the                information/content to be sent to clients 104 for                display; and    -   a search module 238 for enabling users of the social-network        system to search for content and other users in the social        network.

The social network database 214 stores data associated with the socialnetwork in one or more types of databases, such as graph, dimensional,flat, hierarchical, network, object-oriented, relational, and/or XMLdatabases.

In some embodiments, the social network database 214 includes a graphdatabase, with entity information 216 represented as nodes in the graphdatabase and connection information 220 represented as edges in thegraph database. The graph database includes a plurality of nodes, aswell as a plurality of edges that define connections betweencorresponding nodes. In some embodiments, the nodes and/or edgesthemselves are data objects that include the identifiers, attributes,and information for their corresponding entities, some of which arerendered at clients 104 on corresponding profile pages or other pages inthe social-networking service. In some embodiments, the nodes alsoinclude pointers or references to other objects, data structures, orresources for use in rendering content in conjunction with the renderingof the pages corresponding to the respective nodes at clients 104.

Entity information 216 includes user information 218, such as userprofiles, login information, privacy and other preferences, biographicaldata, and the like. In some embodiments, for a given user, the userinformation 218 includes the user's name, profile picture, contactinformation, birth date, sex, marital status, family status, employment,education background, preferences, interests, and/or other demographicinformation.

In some embodiments, entity information 216 includes information about aphysical location (e.g., a restaurant, theater, landmark, city, state,or country), real or intellectual property (e.g., a sculpture, painting,movie, game, song, idea/concept, photograph, or written work), abusiness, a group of people, and/or a group of businesses. In someembodiments, entity information 216 includes information about aresource, such as an audio file, a video file, a digital photo, a textfile, a structured document (e.g., web page), or an application. In someembodiments, the resource is located in the social-network system 108(e.g., in content 222) or on an external server, such as third-partyserver 110.

In some embodiments, connection information 220 includes informationabout the relationships between entities in the social network database214. In some embodiments, connection information 220 includesinformation about edges that connect pairs of nodes in a graph database.In some embodiments, an edge connecting a pair of nodes represents arelationship between the pair of nodes.

In some embodiments, an edge includes or represents one or more dataobjects or attributes that correspond to the relationship between a pairof nodes. For example, when a first user indicates that a second user isa “friend” of the first user, the social-network system 108 transmits a“friend request” to the second user. If the second user confirms the“friend request,” the social-network system 108 creates and stores anedge connecting the first user's user node and the second user's usernode in a graph database as connection information 220 that indicatesthat the first user and the second user are friends. In someembodiments, connection information 220 represents a friendship, afamily relationship, a business or employment relationship, a fanrelationship, a follower relationship, a visitor relationship, asubscriber relationship, a superior/subordinate relationship, areciprocal relationship, a non-reciprocal relationship, another suitabletype of relationship, or two or more such relationships.

In some embodiments, an edge between a user node and another entity noderepresents connection information about a particular action or activityperformed by a user of the user node towards the other entity node. Forexample, a user may “like” or have “attended,” “played,” “listened,”“cooked,” “worked at,” or “watched” the entity at the other node. Thepage in the social-networking service that corresponds to the entity atthe other node may include, for example, a selectable “like,” “checkin,” or “add to favorites” icon. After the user clicks one of theseicons, the social-network system 108 may create a “like” edge, “checkin” edge, or a “favorites” edge in response to the corresponding useraction. As another example, the user may listen to a particular songusing a particular application (e.g., an online music application). Inthis case, the social-network system 108 may create a “listened” edgeand a “used” edge between the user node that corresponds to the user andthe entity nodes that correspond to the song and the application,respectively, to indicate that the user listened to the song and usedthe application. In addition, the social-network system 108 may create a“played” edge between the entity nodes that correspond to the song andthe application to indicate that the particular song was played by theparticular application.

In some embodiments, content 222 includes text (e.g., ASCII, SGML,HTML), images (e.g., jpeg, tif and gif), graphics (e.g., vector-based orbitmap), audio, video (e.g., mpeg), other multimedia, and/orcombinations thereof. In some embodiments, content 222 includesexecutable code (e.g., games executable within a browser window orframe), podcasts, links, and the like.

In some embodiments, the social network server module 228 includes webor Hypertext Transfer Protocol (HTTP) servers, File Transfer Protocol(FTP) servers, as well as web pages and applications implemented usingCommon Gateway Interface (CGI) script, PHP Hyper-text Preprocessor(PHP), Active Server Pages (ASP), Hyper Text Markup Language (HTML),Extensible Markup Language (XML), Java, JavaScript, AsynchronousJavaScript and XML (AJAX), XHP, Javelin, Wireless Universal ResourceFile (WURFL), and the like.

FIG. 3 is a block diagram illustrating an exemplary client device 104 inaccordance with some embodiments. The client device 104 typicallyincludes one or more processing units (processors or cores) 302, one ormore network or other communications interfaces 304, memory 306, and oneor more communication buses 308 for interconnecting these components.The communication buses 308 optionally include circuitry (sometimescalled a chipset) that interconnects and controls communications betweensystem components. The client device 104 includes a user interface 310.The user interface 310 typically includes a display device 312. In someembodiments, the client device 104 includes inputs such as a keyboard,mouse, and/or other input buttons 316. Alternatively or in addition, insome embodiments, the display device 312 includes a touch-sensitivesurface 314, in which case the display device 312 is a touch-sensitivedisplay. In some embodiments, the touch-sensitive surface 314 isconfigured to detect various swipe gestures (e.g., continuous gesturesin vertical and/or horizontal directions) and/or other gestures (e.g.,single/double tap). In client devices that have a touch-sensitivedisplay 312, a physical keyboard is optional (e.g., a soft keyboard maybe displayed when keyboard entry is needed). The user interface 310 alsoincludes an audio output device 318, such as speakers or an audio outputconnection connected to speakers, earphones, or headphones. Furthermore,some client devices 104 use a microphone and voice recognition tosupplement or replace the keyboard. Optionally, the client device 104includes an audio input device 320 (e.g., a microphone) to capture audio(e.g., speech from a user). Optionally, the client device 104 includes alocation detection device 322, such as a GPS (global positioningsatellite) or other geo-location receiver, for determining the locationof the client device 104. The client device 104 also optionally includesan image/video capture device 324, such as a camera or webcam.

Memory 306 includes high-speed random-access memory, such as DRAM, SRAM,DDR RAM or other random-access solid-state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid-state storage devices. Memory 306 may optionallyinclude one or more storage devices remotely located from theprocessor(s) 302. Memory 306, or alternately the non-volatile memorydevice(s) within memory 306, includes a non-transitory computer-readablestorage medium. In some embodiments, memory 306 or the computer-readablestorage medium of memory 306 stores the following programs, modules anddata structures, or a subset or superset thereof:

-   -   an operating system 326 that includes procedures for handling        various basic system services and for performing hardware        dependent tasks;    -   a network communication module 328 that is used for connecting        the client device 104 to other computers via the one or more        communication network interfaces 304 (wired or wireless) and one        or more communication networks, such as the Internet, cellular        telephone networks, mobile data networks, other wide area        networks, local area networks, metropolitan area networks, and        so on;    -   an image/video capture module 330 (e.g., a camera module) for        processing a respective image or video captured by the        image/video capture device 324, where the respective image or        video may be sent or streamed (e.g., by a client application        module 336) to the social-network system 108;    -   an audio input module 332 (e.g., a microphone module) for        processing audio captured by the audio input device 320, where        the respective audio may be sent or streamed (e.g., by a client        application module 336) to the social-network system 108;    -   a location detection module 334 (e.g., a GPS, Wi-Fi, or hybrid        positioning module) for determining the location of the client        device 104 (e.g., using the location detection device 322) and        providing this location information for use in various        applications (e.g., social network client module 340); and    -   one or more client application modules 336, including the        following modules (or sets of instructions), or a subset or        superset thereof:        -   a web browser module 338 (e.g., Internet Explorer by            Microsoft, Firefox by Mozilla, Safari by Apple, or Chrome by            Google) for accessing, viewing, and interacting with web            sites (e.g., a social-networking web site provided by the            social-network system 108, and/or web sites that are linked            to in a social network module 340 and/or an optional client            application module 342), such as accessing a web site            hosting a service for displaying and accessing content            (e.g., stories, such as news articles, posts, etc. as shown            in FIGS. 4A-4H);        -   a social network module 340 for providing an interface to a            social-networking service (e.g., a social-networking service            provided by social-network system 108) and related features,            such as an interface to a service for displaying and            accessing content (e.g., stories, such as news articles,            posts, etc. as shown in FIGS. 4A-4H); and/or        -   optional client application modules 342, such as            applications for displaying and accessing content (e.g.,            stories, such as news articles, posts, etc. as shown in            FIGS. 4A-4H), word processing, calendaring, mapping,            weather, stocks, time keeping, virtual digital assistant,            presenting, number crunching (spreadsheets), drawing,            instant messaging, e-mail, telephony, video conferencing,            photo management, video management, a digital music player,            a digital video player, 2D gaming, 3D (e.g., virtual            reality) gaming, electronic book reader, and/or workout            support.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functions asdescribed above and/or in the methods described in this application(e.g., the computer-implemented methods and other information processingmethods described herein). These modules (i.e., sets of instructions)need not be implemented as separate software programs, procedures ormodules, and thus various subsets of these modules are, optionally,combined or otherwise re-arranged in various embodiments. In someembodiments, memory 206 and/or 306 store a subset of the modules anddata structures identified above. Furthermore, memory 206 and/or 306optionally store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of graphical userinterfaces (“GUIs”) and associated processes that may be implemented ona client device (e.g., the client device 104 in FIG. 3).

FIGS. 4A-4H illustrate exemplary GUIs on a client device 104 forproviding user feedback, in accordance with some embodiments. The GUIsin these figures are used to illustrate the processes described below,including the methods 500 (FIGS. 5A-5B) and 530 (FIGS. 5C-5E). WhileFIGS. 4A-4H illustrate examples of GUIs, in other embodiments, one ormore GUIs displays user-interface elements in arrangements distinct fromthe embodiments of FIGS. 4A-4H.

The GUIs shown in FIGS. 4A-4H may be provided by a web browser (e.g.,browser module 338, FIG. 3), an application for a social-networkingservice (e.g., social network module 340), and/or a third-partyapplication (e.g., client application module 342).

FIG. 4A illustrates a GUI for displaying a first story 400-1 and asecond story 400-2. Stories include electronic content that can bepresented and displayed on a device, such as text comments (e.g., newsarticles, blog posts, documents) and/or multimedia (e.g., digitalphotos, videos, audio files). Stories may include web pages, or contentpublished by users of a social network (e.g., wall posts, statusupdates, check-ins, comments) or by other publication sources (e.g.,news agencies, blogs). In some embodiments, stories are created by auser's interaction with other stories, such as a user providing feedback(e.g., a comment, “like,” etc.) for a news article through asocial-networking service. For example, the first story 400-1 in FIG. 4Aincludes the second story 400-2 (a news article) and an indication of aprevious user interaction with the second story 400-2 that resulted increation of the first story 400-1 (e.g., user 402-1 provides comment412-1, which is a portion of comment 412-3, FIG. 4E).

The GUI in FIG. 4A also concurrently displays multiple user-feedbackinterfaces (UFIs) (e.g., a first UFI 420 and a second UFI 430). Auser-feedback interface provides an interface through which userfeedback for a respective story is received. In this example, the firstUFI 420 receives user feedback for the first story 400-1, and the secondUFI 430 receives user feedback for the second story 400-2. In someembodiments, user-feedback interfaces include one or more affordancesfor providing user feedback (e.g., a recommendation affordance 408-1 anda share affordance 408-2 of the second UFI 430). In some embodiments,user-feedback interfaces display user feedback for a respective story(e.g., a comment, “likes”). For example, the first UFI 420 displays acomment 412-1 (which is a portion of the comment 412-3, FIG. 4E) for thesecond story 400-2 provided by user 402-1, which resulted in thecreation of the first story 400-1. The first UFI 420 and the second UFI430 also display users who have “liked” the respective stories (e.g.,users 402-2 and 402-3 “liked” the first story 400-1, and users 404-1 and404-2 “liked” the second story 400-2), and also display indicators(e.g., 406-1, 406-2) which indicate the number of users who have “liked”the respective stories (e.g., excluding those already displayed by theUFIs).

User-feedback interfaces may be displayed in a compressed view (e.g.,the first UFI 420 and the second UFI 430 as shown in FIG. 4A).Additionally and/or alternatively, user-feedback interfaces may bedisplayed in expanded views, such as a partially expanded view (e.g.,the first UFI 420 as shown in FIGS. 4C and 4D, and the second UFI 430 asshown in FIG. 4G) or a fully expanded view (e.g., the first UFI 420 asshown in FIG. 4E, and the second UFI 430 as shown in FIG. 4H). As shownby the examples of FIGS. 4B-4H, expanded views of a UFI may includeadditional or alternative user feedback and/or affordances that are notdisplayed by the compressed view (or another partially/fully expandedview). Expanded views of a UFI may also display increased portions ofuser feedback that are only partially displayed by the compressed view(e.g., displaying an entire comment in the expanded view, whiledisplaying only a portion of the comment in the compressed view).

In this example, a downward swipe gesture 414-1 detected in FIG. 4Bbeginning in the first UFI 420 results in switching from displaying acompressed view of the first UFI 420 (FIG. 4B) to displaying a partiallyexpanded view of the first UFI 420 (FIG. 4C). As shown, the partiallyexpanded view in FIG. 4C displays user feedback that was displayed bythe compressed view in FIG. 4B (e.g., “likes” by users 402-2 and 402-3,comment 412-1), and also displays user feedback that was not displayedby the compressed view (e.g., comments 422-1 and 422-2). Furthermore,the partially expanded view in FIG. 4C also includes affordances thatwere not displayed by the compressed view (e.g., comment affordance424-1 and “like” affordance 424-2), and additional affordances forproviding feedback for displayed user feedback (e.g., “like” affordances424-3 for “liking” the comment 422-1 for the first story 400-1).

FIG. 4D illustrates another partially expanded view of the first UFI420. In this example, the detection of the same swipe gesture 414-1initiated in FIG. 4B continues, and results in switching from displayingthe partially expanded view of the first UFI 420 (FIG. 4C) to displayinga further expanded, but still partially expanded view of the first UFI420 (FIG. 4D). In addition to the user feedback and affordancesdisplayed in the partially expanded view in FIG. 4C, the partiallyexpanded view in FIG. 4D includes comment 412-2, which is a largerportion of the entire comment 412-3 than the comment 412-1 (FIG. 4A).The partially expanded view in FIG. 4D also displays user feedback of aset of users (e.g., “likes” by a set of users 402), of which users 402-2and 402-3 are a subset (as shown in the compressed view of FIG. 4A, andthe partially expanded view in FIG. 4C).

FIG. 4E illustrates a fully expanded view of the first UFI 420. Here,the continued detection (e.g., completion) of the swipe gesture 414-1initiated in FIG. 4B results in switching from displaying a partiallyexpanded view of the first UFI 420 (FIG. 4D) to displaying a fullyexpanded view of the first UFI 420 (FIG. 4E). In addition to the userfeedback and affordances displayed in the partially expanded view inFIG. 4D, the fully expanded view in FIG. 4E includes the entire comment412-3 (which resulted in creation of the first story 400-1).

Referring now to FIG. 4F, detecting the swipe gesture 414-2 results inswitching from displaying a compressed view of the second UFI 430 (FIG.4F) to displaying a partially expanded view of the second UFI 430 (FIG.4G). As shown, the partially expanded view in FIG. 4G displays userfeedback that was displayed by the compressed view in FIG. 4F (e.g.,“likes” by users 404-1 and 404-2, and indicator 406-2), and alsodisplays additional user feedback that was not displayed by thecompressed view (e.g., comment 432-1, and “likes” by a set of users 404,of which users 404-1 and 404-2 are a subset). Furthermore, the partiallyexpanded view in FIG. 4F also includes affordances that were notdisplayed by the compressed view (e.g., comment affordance 434-1 and“like” affordance 434-2), and additional affordances for providingfeedback for displayed user feedback (e.g., “like” affordances 434-3 for“liking” the comment 432-1 for the second story 400-2).

FIG. 4H illustrates a fully expanded view of the second UFI 430. Here,continued detection (e.g., completion) of the same swipe gesture 414-2initiated in FIG. 4F results in switching from displaying a partiallyexpanded view of the second UFI 430 (FIG. 4G) to displaying a fullyexpanded view of the second UFI 430 (FIG. 4H). In addition to the userfeedback and affordances displayed in the partially expanded view inFIG. 4G, the fully expanded view in FIG. 4H displays additional userfeedback (e.g., comments 432-2 through 432-4).

The examples shown in FIGS. 4A-4H illustrate one order in whichadditional and/or alternative user feedback and affordances aredisplayed when switching from a compressed to a partially expanded view,or from a partially expanded to a fully expanded view (e.g., for thefirst UFI 420, in response to detecting the swipe gesture 414-1,“Comments” are first displayed (FIG. 4C), then additional users who“liked” the story are displayed (FIG. 4D), and then the entire comment412-3 is displayed (FIG. 4E)). In other embodiments, user feedback andaffordances may be displayed in an order distinct from the examples ofFIGS. 4A-4H and may include additional and/or alternative user feedbackand affordances.

FIGS. 5A-5E are flow diagrams illustrating methods 500 (FIGS. 5A-5B) and530 (FIGS. 5C-5E) for providing user feedback, in accordance with someembodiments. The methods 500 and 530 are performed on a client device(e.g., client device 104, FIGS. 1 and 3) and may be performed inconjunction with each other (e.g., such that they together compose asingle method). FIGS. 5A-5E correspond to instructions stored in acomputer memory (e.g., memory 306 of the client device 104, FIG. 3) orother computer-readable storage medium. To assist with describing themethods 500 and 530, FIGS. 5A-5E will be described with reference to theexemplary GUIs illustrated in FIGS. 4A-4H.

In performing the method 500, the client device displays (502) a firststory. The first story includes a second story and an indication of aprevious user interaction with the second story that resulted increation of the first story. As described above, stories includeelectronic content that can be presented and displayed on a device, suchas text comments (e.g., news articles, blog posts, documents) and/ormultimedia (e.g., digital photos, videos, audio files). In someembodiments, the previous user interaction includes (504) sharing, by auser, of the second story. For example, a user may utilize a feature ona social-networking service to republish a story to other users of thesocial-networking service (e.g., by selecting a share affordance 408-2or a recommend affordance 408-1 in FIG. 4A, an article is republishedand appears in the content feeds of the user's friends). In someembodiments, the previous user interaction includes (506) providing, bya user, of user feedback for the second story. For example, a user maycomment on (e.g., by selecting a comment affordance 434-1 and enteringtext, FIG. 4G) or “like” a story (e.g., by selecting a “like” affordance434-2, FIG. 4G). Other examples of user feedback include but are notlimited to sharing and recommending. An example is shown in FIG. 4A,where the client device 104-1 displays a first story 400-1, whichincludes a second story 400-2 (e.g., an article titled “Doe AwardedNobel Peace Prize”) and an indication of a previous user interactionwith the second story 400-2 that resulted in creation of the first story400-1 (e.g., an interaction by a user, “Frances,” who previouslycommented on the article with comment 412-1).

The client device concurrently displays (508) a first user-feedbackinterface (UFI) corresponding to the first story and a seconduser-feedback interface corresponding to the second story. The first UFIincludes (510) one or more first affordances for providing user feedbackregarding the first story (e.g., comment affordance 424-1 and “like”affordance 424-2, FIG. 4C), and the second user-feedback interfaceincludes one or more second affordances for providing user feedbackregarding the second story (e.g., recommend affordance 408-1 and shareaffordance 408-2, FIG. 4A). Therefore, a user is simultaneouslypresented with the option of providing user feedback for either thefirst story 400-1 by using the first UFI 420, or the second story 400-2by using the second UFI 430 (FIG. 4A). FIGS. 4A through 4H illustratemultiple embodiments of a first UFI 420 and a second UFI 430 incompressed, partially expanded, and fully expanded views.

In some embodiments, the first UFI includes (512) an indication of afirst user associated with the previous user interaction with the secondstory that resulted in creation of the first story. For example, asshown in FIG. 4A, the first UFI 420 provides an indication of the userassociated with the comment 412-1 (“Frances,” as represented by thedisplayed user name and icon).

In some embodiments, the first UFI includes (514) user feedback of oneor more users for the first story, not including the first user. Forexample, the first UFI 420 (FIG. 4A) displays users who have “liked” thefirst story 400-1 (e.g., users 402-2 and 402-3). Optionally, the firstUFI 420 also displays an indicator 406-1 that indicates the number ofusers (e.g., excluding those already displayed by the UFIs, such asusers 402-2 and 402-3) who have “liked” the respective stories (e.g.,indicator 406-1 indicates that five other users have “liked” the firststory 400-1, FIG. 4A).

In some embodiments, displaying the first user-feedback interfaceincludes (516) displaying at least a portion of user feedback for thesecond story. The user feedback is provided by the first user in theprevious user interaction with the second story that resulted increation of the first story. For example, as shown in FIG. 4A, the firstUFI 420 displays comment 412-1 (e.g., “What an inspirational wom . . .”), which is a portion of the full comment 412-3 (FIG. 4E) provided bythe user, “Frances,” for the second story 400-2.

In some embodiments, displaying the second user-feedback interfaceincludes (518) displaying user feedback of one or more users for thesecond story. For example, the second UFI 430 (FIG. 4A) displays userswho have “liked” the second story 400-1 (e.g., users 404-1 and 404-2),and optional indicator 406-2 that indicates the number of additionalusers who have “liked” the story (e.g., over one thousand additionalusers).

Referring now to FIG. 5B, the client device receives (520) user feedbackfor the first story through the first user-feedback interface or for thesecond story through the second user-feedback interface. When the userfeedback is received through the first UFI, notification is sent (522)to a server to associate the user feedback with the first story. Whenthe user feedback is received through the second user-feedbackinterface, notification is sent (524) to the server to associate theuser feedback with the second story. For example, a server (e.g., socialnetwork system 108 providing a social-networking service, FIGS. 1 and 2)is provided with an indication of the UFI through which user feedback isreceived, along with an indication of the user feedback itself. Based onthis indication, the server (e.g., social network system 108, FIG. 2)associates the user feedback with its corresponding story. Furthermore,user feedback may cause the server to create a new story that includesthe corresponding story and the user feedback.

Referring now to FIG. 5C, in performing the method 530, the clientdevice displays (502) a first story and concurrently displays (508) afirst user-feedback interface (UFI) corresponding to the first story anda second user-feedback interface corresponding to the second story, asdiscussed above with respect to the method 500).

In some embodiments, the client device displays (532) compressed viewsof the first and/or second user-feedback interfaces. Examples ofcompressed views of a first UFI 420 and a second UFI 430 are shown inFIG. 4A.

In some embodiments, the compressed view of the first UFI includes (534)a portion of user feedback for the second story provided by a first userin the previous user interaction that resulted in creation of the firststory. For example, the compressed view of the first UFI 420 (FIG. 4A)includes comment 412-1, which is a portion of the full comment 412-3(FIG. 4E). In some embodiments, the compressed view of the first UFIincludes (536) user feedback of a first set of users, not including thefirst user, for the first story (e.g., users 402-2 and 402-3, FIG. 4A).In some embodiments, the compressed view of the first UFI includes (538)the one or more first affordances. In some embodiments, the compressedview of the first UFI shows (540) a first type of user feedback (e.g., acomment 412-1 for the second story 400-2, “likes” by users 402-2 and402-3, FIG. 4A).

In some embodiments, the compressed view of the second UFI includes(542) user feedback of a first set of users for the second story. Insome embodiments, the first set of users who provided feedback for thesecond story includes at least some users distinct from the first set ofusers who provided (536) feedback for the first story. In someembodiments, the compressed view of the second UFI includes (544) theone or more second affordances (e.g., recommend affordance 408-1 andshare affordance 408-2, FIG. 4A). In some embodiments, the compressedview of the second UFI shows (546) a first type of user feedback (e.g.,“likes” by users 404-1 and 404-2, FIG. 4A).

In some embodiments, the client device detects (548) selection of thefirst or second user-feedback interface. For example, the client devicedetects (550) a continuous swipe gesture beginning on the first orsecond user-feedback interface (e.g., swipe gesture 414-1 beginning onthe first UFI 420). In some embodiments, the continuous swipe gesture isa substantially vertical swipe (e.g., within a specified number ofdegrees of vertical), as shown for the swipe gesture 414-1. In someembodiments, the swipe gesture is a touch-screen input (e.g., detectedby the touch-sensitive surface 314 of client device 104, FIG. 3). Theswipe gesture may also be detected by other input devices (e.g., atouchpad). Alternatively and/or additionally, selection of the first orsecond UFI may include other touch inputs (e.g., a tap).

In some embodiments, in response to detecting the selection of the firstuser-feedback interface, the client device displays (552, FIG. 5D) anexpanded view of the first user-feedback interface. For example, in FIG.4B, detecting a downward swipe gesture 414-1 starting on the first UFI420 results in switching from displaying a compressed view of the firstUFI 420 (FIG. 4B) to displaying a partially expanded view of the firstUFI 420 (FIGS. 4C and 4D) and then a fully expanded view of the firstUFI 420 (FIG. 4E).

In some embodiments, the expanded view of the first UFI includes (554)the user feedback for the second story provided by the first user (e.g.,comment 412-3 by user 402-1, FIG. 4C, of which comment 412-1 is aportion, as shown in FIG. 4A).

In some embodiments, the expanded view of the first UFI includes (556)user feedback of a second set of users for the first story, wherein thefirst set of users (536) is a subset of the second set of users. Forexample, in the partially expanded view in FIG. 4D and the fullyexpanded view in FIG. 4E, the set of users 402 who have “liked” thefirst story 400-1 includes the users 402-2 and 402-3, whose “likes” arealso shown in the compressed view of the first UFI 420 in FIG. 4B. Thepartially expanded view of the first UFI 420 therefore displays moreuser feedback (e.g., more “likes”) than the compressed view. In someembodiments, the second set of users is a subset of a third set of users(e.g., third set includes all users who have “liked” or providedfeedback for a respective story).

In some embodiments, the expanded view of the first UFI includes (558)the one or more first affordances (510, FIG. 5A) and one or more thirdaffordances for providing user feedback regarding the first story,wherein the one or more first affordances are distinct from the one ormore third affordances. In some embodiments, respective affordances ofthe one or more first affordances and the one or more third affordancesare selected (560) from the group consisting of an affordance forrecommending the first story, an affordance for sharing the first story,an affordance for commenting on the first story (e.g., 424-1, FIG. 4C),and an affordance for “liking” the first story (e.g., 424-2, FIG. 4C).For example, the compressed view of the first UFI 420 may include ashare affordance (not shown in FIG. 4A-4H), while a partially or fullyexpanded view (FIGS. 4C-4E) includes a comment affordance 424-1 and a“like” affordance 424-2 that are not included in the compressed view.

In some embodiments, the client device displays (562), while detectingthe continuous swipe gesture, an increasing portion of the expanded viewof the first user-feedback interface until the entire expanded view ofthe first user-feedback interface is displayed. An example is shown inFIGS. 4B-4E, where a continuous swipe gesture 414-1 is first detected(FIG. 4B), and the partially expanded view of the first UFI 420increases (FIGS. 4C through 4D) with the continued detection of theswipe gesture 414-1 until the fully expanded view of the first UFI 420is displayed (FIG. 4E). In some embodiments, the amount of userfeedback, the number of affordances, and/or the number of additionalelements displayed in an expanded view of the first UFI increases with(e.g., is proportional to) the magnitude of the swipe gesture (e.g.,total screen distance traversed by the swipe gesture). The amount ofuser feedback shown thus may be a function of how much of the expandedview has been dragged into view by the user. The expanded view istherefore populated with more and/or additional types of user feedbackthe longer the swipe gesture is dragged out, until the full expandedview is shown or the swipe gesture ends. For example, the partiallyexpanded view in FIG. 4D displays more user feedback (e.g., more userswho have “liked” the first story 400-1) than the partially expanded viewin FIG. 4C because the magnitude of the swipe gesture 414-1 (as measuredrelative to the first detection in FIG. 4B) is greater in FIG. 4D thanin FIG. 4C.

In some embodiments, the expanded view of the first UFI shows (564) thefirst type of user feedback (540) and a second type of user feedback,distinct from the first type of user feedback. For example, a compressedview of the first UFI may display user “likes” of a first story (a firsttype of user feedback), while a partially or fully expanded view of thefirst UFI displays both user “likes” and user comments for the firststory (a second type of user feedback).

The client device receives (520) user feedback for the first storythrough the first user-feedback interface or for the second storythrough the second user-feedback interface. When the user feedback isreceived through the first UFI, notification is sent (522) to a serverto associate the user feedback with the first story. When the userfeedback is received through the second user-feedback interface,notification is sent (524) to the server to associate the user feedbackwith the second story. Receiving user feedback (520) and sendingnotifications to the server (522 and 524) are performed in accordancewith any of the embodiments discussed above with respect to the method500.

In some embodiments, in response to detecting (548, FIG. 5C) theselection on the second user-feedback interface, the client devicedisplays (566, FIG. 5E) an expanded view of the second user-feedbackinterface. For example, in FIG. 4F, detecting an upward swipe gesture414-2 starting on the second UFI 430 results in switching fromdisplaying a compressed view of the second UFI 430 (FIG. 4F) todisplaying a partially expanded view of the second UFI 430 (FIG. 4G) andthen a fully expanded view of the second UFI 430 (FIG. 4H).

In some embodiments, the expanded view of the second UFI includes (568)user feedback of a second set of users for the second story, wherein thefirst set of users (542) is a subset of the second set of users. Forexample, in the partially expanded view in FIG. 4G and the fullyexpanded view in FIG. 4H, the set of users 404 who have “liked” thesecond story 400-1 includes the users 404-1 and 404-2, whose “likes” arealso shown in the compressed view of the second UFI 430 in FIG. 4F. Insome embodiments, the second set of users is a subset of a third set ofusers (e.g., third set includes all users who have “liked” or providedfeedback for a respective story).

In some embodiments, the expanded view of the second UFI includes (570)the one or more second affordances (510, FIG. 5A) and one or more fourthaffordances for providing user feedback regarding the second story,wherein the one or more second affordances are distinct from the one ormore fourth affordances. In some embodiments, respective affordances ofthe one or more second affordances and the one or more fourthaffordances are selected (572) from the group consisting of anaffordance for recommending the second story (e.g., 408-1, FIG. 4A), anaffordance for sharing the second story (e.g., 408-2, FIG. 4A), anaffordance for commenting on the second story (e.g., 434-1, FIG. 4G),and an affordance for “liking” the second story (e.g., 434-2, FIG. 4G).For example, the compressed view of the second UFI 430 (FIG. 4A)includes a recommend affordance 408-1 and a share affordance 408-2,while a partially or fully expanded view (FIGS. 4G-4H) includes acomment affordance 434-1 and a “like” affordance 434-2 that are notincluded in the compressed view.

In some embodiments, the client device displays (574), while detectingthe continuous swipe gesture, an increasing portion of the expanded viewof the second user-feedback interface until the entire expanded view ofthe second user-feedback interface is displayed. An example is shown inFIGS. 4F-4H, where a continuous swipe gesture 414-2 is first detected(FIG. 4F), and the partially expanded view of the second UFI 420increases (FIG. 4G) with the continued detection of the swipe gesture414-2 until the fully expanded view of the second UFI 430 is displayed(FIG. 4H). In some embodiments, the amount of user feedback, the numberof affordances, and/or the number of additional elements displayed in anexpanded view of the second UFI increases with (e.g., is proportionalto) the magnitude of the swipe gesture (e.g., total screen distancetraversed since the first detection of the swipe gesture).

In some embodiments, the expanded view of the second UFI shows (576) thefirst type (546) of user feedback (e.g., user “likes”) and a second typeof user feedback (e.g., user comments), distinct from the first type ofuser feedback.

The client device receives (520) user feedback for the first storythrough the first user-feedback interface or for the second storythrough the second user-feedback interface. When the user feedback isreceived through the first UFI, notification is sent (522) to a serverto associate the user feedback with the first story. When the userfeedback is received through the second user-feedback interface,notification is sent (524) to the server to associate the user feedbackwith the second story. Receiving user feedback (520) and sendingnotifications to the server (522 and 524) are performed in accordancewith any of the embodiments discussed above with respect to the method500.

For situations in which the systems discussed above collect informationabout users, the users may be provided with an opportunity to opt in/outof programs or features that may collect personal information (e.g.,information about a user's preferences or a user's contributions tosocial content providers). In addition, in some embodiments, certaindata may be anonymized in one or more ways before it is stored or used,so that personally identifiable information is removed. For example, auser's identity may be anonymized so that the personally identifiableinformation cannot be determined for or associated with the user, and sothat user preferences or user interactions are generalized (for example,generalized based on user demographics) rather than associated with aparticular user.

Although some of various drawings illustrate a number of logical stagesin a particular order, stages which are not order dependent may bereordered and other stages may be combined or broken out. While somereordering or other groupings are specifically mentioned, others will beapparent to those of ordinary skill in the art, so the ordering andgroupings presented herein are not an exhaustive list of alternatives.Moreover, it should be recognized that the stages could be implementedin hardware, firmware, software or any combination thereof.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the scope of the claims to the precise forms disclosed. Manymodifications and variations are possible in view of the aboveteachings. The embodiments were chosen in order to best explain theprinciples underlying the claims and their practical applications, tothereby enable others skilled in the art to best use the embodimentswith various modifications as are suited to the particular usescontemplated.

What is claimed is:
 1. A method, comprising: at a client device havingone or more processors and memory storing one or more programsconfigured for execution by the one or more processors: displaying afirst story, wherein the first story comprises a republication of asecond story and an indication of a previous user interaction with thesecond story that resulted in creation of the first story; concurrentlywith displaying the first story, displaying a compressed view of a firstuser-feedback interface, corresponding to the first story, including oneor more corresponding first affordances for providing user feedbackregarding the first story, and displaying a compressed view of a seconduser-feedback interface, corresponding to the second story, includingone or more corresponding second affordances for providing user feedbackregarding the second story; detecting user selection of either the firstuser-feedback interface or the second user-feedback interface; inresponse to detecting the user selection, displaying an expanded view ofthe selected user-feedback interface concurrently with displaying thecompressed view of the user-feedback interface not selected, theexpanded view of the selected user-feedback interface including the oneor more first affordances, or the one or more second affordances,corresponding to the selected user-feedback interface and replacing atleast a portion of the story corresponding to the user-feedbackinterface not selected.
 2. The method of claim 1, wherein the firstuser-feedback interface further comprises: an indication of a first userassociated with the previous user interaction with the second story thatresulted in creation of the first story, and user feedback of one ormore users, not including the first user, for the first story.
 3. Themethod of claim 1, wherein the previous user interaction comprisessharing, by a first user, of the second story.
 4. The method of claim 1,wherein the previous user interaction comprises providing, by a firstuser, of user feedback for the second story.
 5. The method of claim 4,wherein displaying the first user-feedback interface comprisesdisplaying at least a portion of the user feedback for the second storyprovided by the first user in the previous user interaction with thesecond story that resulted in creation of the first story.
 6. The methodof claim 1, wherein: the compressed view of the first user-feedbackinterface comprises: a portion of user feedback for the second storyprovided by a first user in the previous user interaction that resultedin creation of the first story; and indication of user feedback of afirst set of users, not including the first user, for the first story;and the expanded view of the first user-feedback interface comprises:the user feedback for the second story provided by the first user; anduser feedback of a second set of users for the first story, wherein thesecond set of users is a subset of the first set of users.
 7. The methodof claim 1, wherein: the compressed view of the first user-feedbackinterface comprises the one or more first affordances; and the expandedview of the first user-feedback interface comprises the one or morefirst affordances and one or more third affordances for providing userfeedback regarding the first story, wherein the one or more firstaffordances are distinct from the one or more third affordances.
 8. Themethod of claim 7, wherein respective affordances of the one or morefirst affordances and the one or more third affordances are selectedfrom the group consisting of an affordance for recommending the firststory, an affordance for sharing the first story, an affordance forcommenting on the first story, and an affordance for liking the firststory.
 9. The method of claim 1, wherein: detecting the user selectioncomprises detecting a continuous swipe gesture beginning on the firstuser-feedback interface; and displaying the expanded view of the firstuser-feedback interface comprises displaying, while detecting thecontinuous swipe gesture, an increasing portion of the expanded view ofthe first user-feedback interface until the entire expanded view of thefirst user-feedback interface is displayed.
 10. The method of claim 1,wherein: the compressed view of the first user-feedback interface showsa first type of user feedback; and the expanded view of the firstuser-feedback interface shows the first type of user feedback and asecond type of user feedback, distinct from the first type of userfeedback.
 11. The method of claim 1, wherein displaying the seconduser-feedback interface comprises displaying user feedback of one ormore users for the second story.
 12. The method of claim 1, wherein: thecompressed view of the second user-feedback interface comprises userfeedback of a first set of users for the second story; and the expandedview of the second user-feedback interface comprises user feedback of asecond set of users for the second story, wherein the first set of usersis a subset of the second set of users.
 13. The method of claim 12,wherein: the compressed view of the second user-feedback interface showsa first type of user feedback; and the expanded view of the seconduser-feedback interfaces shows the first type of user feedback and asecond type of user feedback, distinct from the first type of userfeedback.
 14. The method of claim 1, wherein: the compressed view of thesecond user-feedback interface comprises the one or more secondaffordances; and the expanded view of the second user-feedback interfacecomprises the one or more second affordances and one or more fourthaffordances for providing user feedback regarding the second story,wherein the one or more second affordances are distinct from the one ormore fourth affordances.
 15. The method of claim 14, wherein respectiveaffordances of the one or more second affordances and the one or morefourth affordances are selected from the group consisting of anaffordance for recommending the second story, an affordance for sharingthe second story, an affordance for commenting on the second story, andan affordance for liking the second story.
 16. The method of claim 1,wherein: detecting the user selection comprises detecting a continuousswipe gesture beginning on the second user-feedback interface; anddisplaying the expanded view of the second user-feedback interfacecomprises displaying, while detecting the continuous swipe gesture, anincreasing portion of the expanded view of the second user-feedbackinterface until the entire expanded view of the second user-feedbackinterface is displayed.
 17. A client device, comprising: one or moreprocessors; and memory storing one or more programs configured forexecution by the one or more processors, the one or more programsincluding instructions for: displaying a first story, wherein the firststory comprises a republication of a second story and an indication of aprevious user interaction with the second story that resulted increation of the first story; concurrently with displaying the firststory, displaying a compressed view of a first user-feedback interface,corresponding to the first story, including one or more correspondingfirst affordances for providing user feedback regarding the first story,and displaying a compressed view of a second user-feedback interface,corresponding to the second story, including one or more correspondingsecond affordances for providing user feedback regarding the secondstory; detecting user selection of either the first user-feedbackinterface or the second user-feedback interface; in response todetecting the user selection, displaying an expanded view of theselected user-feedback interface concurrently with displaying thecompressed view of the user-feedback interface not selected, theexpanded view of the selected user-feedback interface including the oneor more first affordances, or the one or more second affordances,corresponding to the selected user-feedback interface and replacing atleast a portion of the story corresponding to the user-feedbackinterface not selected.
 18. The client device of claim 17, wherein: thecompressed view of the first user-feedback interface comprises: aportion of user feedback for the second story provided by a first userin the previous user interaction that resulted in creation of the firststory; and indication of user feedback of a first set of users, notincluding the first user, for the first story; and the expanded view ofthe first user-feedback interface comprises: the user feedback for thesecond story provided by the first user; and user feedback of a secondset of users for the first story, wherein the second set of users is asubset of the first set of users.
 19. A non-transitory computer-readablestorage medium storing one or more programs for execution by one or moreprocessors of a client device, the one or more programs includinginstructions for: displaying a first story, wherein the first storycomprises a republication of a second story and an indication of aprevious user interaction with the second story that resulted increation of the first story; concurrently with displaying the firststory, displaying a compressed view of a first user-feedback interface,corresponding to the first story, including one or more correspondingfirst affordances for providing user feedback regarding the first story,and displaying a compressed view of a second user-feedback interface,corresponding to the second story, including one or more correspondingsecond affordances for providing user feedback regarding the secondstory; detecting user selection of either the first user-feedbackinterface or the second user-feedback interface; in response todetecting the user selection, displaying an expanded view of theselected user-feedback interface concurrently with displaying thecompressed view of the user-feedback interface not selected, theexpanded view of the selected user-feedback interface including the oneor more first affordances, or the one or more second affordances,corresponding to the selected user-feedback interface and replacing atleast a portion of the story corresponding to the user-feedbackinterface not selected.
 20. The computer-readable storage medium ofclaim 19, wherein: the compressed view of the first user-feedbackinterface comprises: a portion of user feedback for the second storyprovided by a first user in the previous user interaction that resultedin creation of the first story; and indication of user feedback of afirst set of users, not including the first user, for the first story;and the expanded view of the first user-feedback interface comprises:the user feedback for the second story provided by the first user; anduser feedback of a second set of users for the first story, wherein thesecond set of users is a subset of the first set of users.